Slug Creation Should Allow Numbers#41
Merged
alfredxing merged 3 commits intojekyll:masterfrom Nov 30, 2015
Merged
Conversation
Member
|
/cc @alfredxing |
Member
|
👍 Not sure how I missed this one... |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I have a site which uses years as tags. Because this value previously checked for String objects only, the slug would not be set, and the value would be nil for later where a crash would occur.
Forcing a to_s and checking length will allow numbers, or pretty much any object that is listed under tags to get through.